test: enforce Intelligence OS ownership boundaries - #129
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Completes the machine-enforced ownership half of ACE 0.8B. Core, Intelligence, and application now have an executable dependency rule, and every top-level package in the historical
core.enginetree has exactly one declared 0.8 owner and compatibility treatment.Changes
ace.corehas no inward Intelligence, application, legacy-host, transport, or extension dependencyace.intelligenceremains pure interpretation without application, host, transport, or extension importsace.applicationcomposes only public portscore.enginepackage and fails if an unowned package appearsEvidence
git diff --check: passedCompatibility and rollback
No runtime API, stored record, schema, Domain Pack, source adapter, public MCP tool, or historical evidence is changed. The disposition manifest classifies the compatibility host; it does not delete or move it. Reverting this commit removes only the new guard and documentation.
Checklist
Part of #40. This is 0.8B2; the final 0.8B restart/legacy-caller convergence remains separate.